Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bugfix/66 graceful crash handling #665

Merged
merged 15 commits into from
May 10, 2024
Merged

Conversation

AssemblyJohn
Copy link
Contributor

Describe your changes

Updated interface usage for CSR generation

Issue ticket number and link

EVerest/libocpp#604
EVerest/libevse-security#70

Checklist before requesting a review

  • I have performed a self-review of my code
  • I have made corresponding changes to the documentation
  • I read the contribution documentation and made sure that my changes meet its requirements

types/evse_security.yaml Outdated Show resolved Hide resolved
description: OCSP data related to requested the certificates
type: object
required:
- hash
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why is the ocsp_path optional?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because if we have a chain of returned certificates, for example leaf<-subca2<-subca1, we agreed that a list of the same count of OCSP data will be returned, because matching the ocsp data to a certificate in everest-core will be very difficult, based on a certificate hash, because it is difficult to build that has, especially when intermediaries are involved. So, if a chain of 3 certificates is returned, then a vector of 3 ocsp data is returned, each matched to the certificate from the chain in order.

interfaces/evse_security.yaml Outdated Show resolved Hide resolved
@AssemblyJohn
Copy link
Contributor Author

Some comments resolved, awaiting further feedback.

@Pietfried Pietfried self-assigned this May 7, 2024
@AssemblyJohn AssemblyJohn force-pushed the bugfix/66-graceful-crash-handling branch from c5d6f37 to db49018 Compare May 7, 2024 09:24
dependencies.yaml Outdated Show resolved Hide resolved
@AssemblyJohn AssemblyJohn force-pushed the bugfix/66-graceful-crash-handling branch 2 times, most recently from f4c0c59 to 72d1f8c Compare May 7, 2024 10:16
Copy link
Contributor

@SirVer SirVer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed for Bazel only. LGTM.

Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
Signed-off-by: AssemblyJohn <[email protected]>
@AssemblyJohn AssemblyJohn force-pushed the bugfix/66-graceful-crash-handling branch from 4229a94 to 5b2a238 Compare May 8, 2024 10:04
Signed-off-by: AssemblyJohn <[email protected]>
@Pietfried Pietfried self-requested a review May 8, 2024 12:05
@@ -146,10 +157,13 @@ cmds:
description: Specifies the encoding of the key
type: string
$ref: /evse_security#/EncodingFormat
include_ocsp:
description: Specifies whether per-certificate OCSP data is also requested
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
description: Specifies whether per-certificate OCSP data is also requested
description: Specifies whether per-certificate OCSP data is also requested

Copy link
Contributor

@SebaLukas SebaLukas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@AssemblyJohn AssemblyJohn merged commit 888aecb into main May 10, 2024
5 checks passed
@AssemblyJohn AssemblyJohn deleted the bugfix/66-graceful-crash-handling branch May 10, 2024 09:29
hikinggrass added a commit that referenced this pull request May 10, 2024
When #665 was merged it did not point to git hashes on the main branch but on a now deleted feature branches
hikinggrass added a commit that referenced this pull request May 10, 2024
When #665 was merged it did not point to git hashes on the main branch but on a now deleted feature branches

Signed-off-by: Kai-Uwe Hermann <[email protected]>
hikinggrass added a commit that referenced this pull request May 10, 2024
When #665 was merged it did not point to git hashes on the main branch but on a now deleted feature branches

Signed-off-by: Kai-Uwe Hermann <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants